Guideline: Tips - Evaluate The Test Process (AST)

Evaluations as leverage for change

The carrying out of evaluations may have a purpose that extends beyond simply reusing the acquired knowledge. It may also have the purpose of setting up the knowledge as leverage for change. A condition for this is that the test manager’s role is one in which he can propose changes. These proposals can then be included in the final report. If this process is already taking place during the execution of the project, there is the great advantage that the changes can be implemented immediately. A condition for success is that the sharing of knowledge be encouraged at every level, this is possible by, for example, organising (informal) meetings. During these meetings, there should be a relaxed and egalitarian atmosphere. Involve all the parties in the meeting, talk about the problems and try to find immediate solutions.

Testers as sounding board

During a test, more and more English-speaking developers came to the Dutchspeaking testers to ask questions concerning particular functional specifications. It appeared from various informal meetings on Friday afternoons that they had difficulty with the combination of the broken English of the Dutch designers and the long screeds of text. From within their expertise, the testers had built up in-depth knowledge of the system. In consultation with the various parties, it was then decided that the testers could serve the developers as a sounding board. In addition, a selection was made from existing test scripts that had to be executed by the developers before they delivered their piece of software. This benefited the general quality and pace of the test process, defects were now found during development and there was a greater involvement of the developers in the testing and vice versa.